AppDynamics

Since AppDynamics is not open source monitoring tool like Nagios, it has many advanced features likes drilling the issues at code level and identifying the potential class and method responsible for the issue save the time of developer instead of going through the entire code, now he has the code line number to fix.
Flow graph of application helps understanding how the services are performing across different tier and which service need improvement.
Setting up health rules is quite dynamic so now you don't have to depend on static number for threshold for triggering alert. Alert can be triggered on the basis of standard deviations and mathematical formula.

AppDynamics monitoring solution is quite expensive so if a medium enterprise who have budget constraints for performance engineering department can check for other open source tools and setting up AppDynamics requires huge infrastructure so procurement of those resources is overhead.

The AI-powered suggestions from AppDynamics were crucial in helping us maximize our use of resources. In order to handle peak traffic, we had to continuously scale up our infrastructure, which resulted in needless expenses. AppDynamics recommended streamlining database queries and caching strategies, which led to a 20% decrease in resource usage without compromising performance. We were able to invest in other areas of our application while saving a substantial amount of money thanks to this.

Organizations seeking a unified platform for monitoring applications, user experiences, infrastructure, and business metrics find AppDynamics suitable. Its centralized approach simplifies monitoring across the entire IT environment.AppDynamics has given us with a competitive edge in the industry. Our technological edge is in our capacity to proactively monitor and improve applications, which allows us to attract clients that place a premium on service dependability and performance.

AppDynamics is well suited for website and application monitoring. It was able to identify some code on our websites that needed to be cleaned up and we were able t configure alerts to send to the relevant server owner when a service went down. It does a very good job with real time performance on you apps. When systems are in non production or 100% uptime is not required it is hard to justify the cost and time to configure AppDymanics

This is my first experience with CISCO AppDynamics, so my concerns might be based on the "first timer" anxiety, But compared to the other Monitoring platforms that I have worked with in the past, Cisco AppDynamics was good in terms of UI. But AppDynamics lacks customization, especially when I am trying to generate a report, it has very less scope for exporting the logs. Although I can customize it once I have downloaded it, customizing it on the platform level itself, would have been helpful.

Apart from that, I was able to test, bring one server down on production and then test the response of Alerts from AppDynamics, there was a slight lag, which I observed, but still, when monitoring multiple servers and gateways, I believe a few seconds of delay might be negotiable.

Will recommend AppDynamics If you need a single tool for monitoring and log analytics. It helps is narrowing down the problem in hand to troubleshoot wether its a hardware, database, connectivity or application issue. Recommended for any large organisation which needed to monitor 100s of services in realtime.

If application breakdown is impacting your business operations and you are unable to identify the root cause of the problem such as whether the issue is because of the hardware, database, network or application, or something else then AppDynamics fits in and provides easy to detect root cause with simple steps of configuration

No doubt AppDynamics is high tech APM solution that offers easy to configure application space monitoring, tracing, mapping also some sort of event collection and monitoring, however, it lacks certain things which I believe are pretty important as the new standards are being evolved for business means one such example is Observability i.e. visibility of not just application but underlying infra, users, platform and correlation among them is what still required in AppDynamics.

The database monitoring piece of the application is not something I would recommend to people mainly because there are far better database monitoring agents available in the market.

I would like to recommend two features that make Appdynamics look strong. For business people and users, it has nice built-in dashboards for mobile and web application monitoring like visitors location details, top requested pages/transactions, error details, etc. For tech ops teams, especially teams in charge of application or infrastructure management; automatic topology discovery is the most important part and helps them to identify issues at first look. It shows you the real-time error rate and application health in a single figure.

Excellent tool for Application monitoring. Can be combined with Performance tests to understand pain points in the application and improve Setting up alarms/notification on an excellent UI is awesome. If you want to fine-tune performance issues looking at various layers of architecture like middle layer, DB layer, etc.., this tool is a perfect fit. Areas that are not best fit - In my opinion, If you want to do infrastructure monitoring AppDynamics is not yet there. Eventually, it will catch up is what I think.

Very well suited for Internet monitoring and for understanding the issues, provides excellent functionality with regards to tracing coding exceptions - errors can easily be drilled down to the method or line of code that is problematic. Very flexible.

Drilling to the root level of the issue is possible with this tool. Project functions are awesome. It integrates well with load runner, [thus] making performance testing a bliss.
It helps finding the bottlenecks from the code as we can extract exact method and class names from the code.
Web applications monitored [is] a breeze. Great analytical dashboards. Monitoring infrastructure is also great using this tool.

This product is great for very big organizations with complicated products that are business critical. For example, for managing and monitoring millions of transactions. It is not a great product if you are trying to monitor small software apps and don't have that much complexity. You can look at other options. Also, it does not make sense if Budget [is] a key factor.

Well suited for managing and reviewing data points across thousands of metrics and being able to zoom into the most granular details for performance investigations. It could be overwhelming for a non-technical user to work with but the visual outputs help share data with them in a way that trends can be understood.

We execute various types of performance testing such as load testing, stress testing, endurance testing, and spike testing on the daily basis in various environments. It was tough to detect and monitor the performance issues for each type of performance testing, but using AppDynamics, it is possible to create a trend in bottleneck detection. When the performance testing projects integrated with CI/CD pipeline, then the AppDynamics plugin helps a lot. for example, if there is a performance degradation, it allows the job to be failed.

We had slowness, but didn't know where. We quickly would find out if it was the network, database, app server, webserver, or otherwise. They don't like me saying this, but it's a great "finger-pointer".

AppDynamics is really good for comprehensive application monitoring and alerting, but does carry a learning curve to get the real value out of it.

AppDynamics is clearly well suited for monitoring e-commerce applications and I can see where it adds huge value for organisations with this application. It is less suited as an entire suite for our application but we do get value from the parts of the application which do suit our application.

AppDynamics is well suited for environments where tolerance for latency is low. Identifying latency and where it is coming from early can make the difference in mean time to detect (MTTD) and mean time to resolve (MTTR).